System and method for event management

ABSTRACT

The event management system described is capable of aligning controlled content in a controlled content repository to properties of an event, e.g., event type, event topic, geographic location and product involved. When a user creates an event, controlled content associated with the event properties may be displayed so that the user may choose proper content for the event. When event content is updated in the controlled content repository, the latest version is pushed to the speaker so that only the latest version of the controlled content can be shared. Content displayed during a webinar and attendee participation data for the webinar may be tracked and stored in a CRM system.

CROSS-REFERENCE TO RELATED APPLICATION

The present application is a continuation-in-part application of U.S.nonprovisional patent application Ser. No. 15/853,344, filed on Dec. 22,2017, entitled System and Method for Event Management, whichincorporates U.S. Pat. No. 9,055,023, entitled System and Method forControlling Electronic Communications and issued on Jun. 9, 2015, byreference for all purposes.

TECHNICAL FIELD

The present application relates to systems and methods for managingevents in the life science industry.

BACKGROUND

In certain fields, the ability to achieve the efficiencies associatedwith modern electronic communications such as webinar has been hamperedby the risks (regulatory and otherwise) of sharing the content. Anexample of one field that has been so limited has been the life scienceindustry, where speakers typically are strictly regulated when sharingcontent with prescribing doctors because of the enormous risks that canflow from unapproved, uncontrolled content.

SUMMARY

Embodiments disclosed in the present document provide amachine-implemented method for event management. The method comprises:establishing a controlled content repository, the controlled contentrepository being securely and controllably accessed. The method furthercomprises: establishing an access protocol for the controlled contentrepository, receiving an input for approving an item of content to beshared during a first event; and storing approved content within thecontrolled content repository, whereby the approved content is stored inthe controlled content repository according to the access protocol andwhereby the access protocol comprises at least one set of alignmentrules for determining if a first item of approved content within thecontrolled content repository can be made available to a first customer.The method further comprises: associating a first item of approvedcontent within the controlled content repository with a first value of afirst event property of the first event from an information managementsystem.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present application and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which like referencenumbers indicate like features.

FIG. 1 illustrates an example architecture for managing events;

FIG. 2 illustrates an example architecture for the content repository ofFIG. 1 in which content is built and organized in a controlled mannerthat facilitates efficient content generation and alignment;

FIGS. 3A, 3B and 3C illustrate a flowchart of a method for managingevents;

FIG. 4 illustrates an example of a user interface for creating a webinarfor an event; and

FIG. 5 illustrates an example of an information screen for an eventdisplayed to a speaker.

FIG. 6 illustrates an example flowchart of a method for processing aremote medical inquiry during an event according to one embodiment ofthe present invention.

Although similar reference numbers may be used to refer to similarelements for convenience, it can be appreciated that each of the variousexample embodiments may be considered to be distinct variations.

The present embodiments will now be described hereinafter with referenceto the accompanying drawings, which form a part hereof, and whichillustrate example embodiments which may be practiced. As used in thedisclosures and the appended claims, the terms “embodiment” and “exampleembodiment” do not necessarily refer to a single embodiment, although itmay, and various example embodiments may be readily combined andinterchanged, without departing from the scope or spirit of the presentembodiments. Furthermore, the terminology as used herein is for thepurpose of describing example embodiments only, and are not intended tobe limitations. In this respect, as used herein, the term “in” mayinclude “in” and “on,” and the terms “a,” “an” and “the” may includesingular and plural references. Furthermore, as used herein, the term“by” may also mean “from,” depending on the context. Furthermore, asused herein, the term “if” may also mean “when” or “upon,” depending onthe context. Furthermore, as used herein, the words “and/or” may referto and encompass any and all possible combinations of one or more of theassociated listed items.

DETAILED DESCRIPTION

In disclosed embodiments, intelligent and flexible updating of recordsmay be provided within the customer relationship management subsystem,including such approaches as communicating with third-party systems andsources in order to verify and update customer information in aneffective and timely manner, such as by using the collective informationgained by managing a cloud-based system/Software-as-a-Service (SaaS)system on behalf of multiple company customers for the disclosedembodiments.

FIG. 1 is a system overview illustrating an embodiment of an eventmanagement system 100. The presently disclosed embodiment comprises acontent management server 101, a controlled content repository 102, aCustomer Relationship Management (CRM) server 106, a multichannelprocessing engine 108, and an event management controller 130. Thecustomer relationship management server 106 may provide access to acustomer relationship management subsystem 104, and the multichannelprocessing engine 108 may be coupled to the content management server101, the CRM server 106, and an email server 114. In one embodiment, thecustomer relationship management subsystem 104, the teleconferencecontroller 131, and/or the email server 114 may be operated by a thirdparty. The multichannel processing engine 108 may be accessed by userssuch as company sales representatives through web clients 110 or throughmobile apps 112 (such as iOS, Android, Blackberry, or Windows Mobilesystems) in user computing devices, communicating with the multichannelprocessing engine 108 through web servers 113. Although the users may bedescribed in the present application as being life science webinarspeakers and company sales representatives, this particular describedembodiment is not intended to limit the generality of the claims thatmay eventually issue in patents stemming from the present disclosure.

The controlled content repository 102 is designed to have a process fordeveloping approved content that is sharable across multiple users, suchas shareholders, reviewers, managers, marketing personnel, physicians,sales representatives, etc. The content generated in the controlledcontent repository 102 may be accessed on a regulated basis. Thisregulated basis may be determined, in part, by the company as a wholeand additionally by interaction with data from the customer relationshipmanagement subsystem 104, described in further detail below. In oneembodiment, approved content, customer profile information, customerpreferences, and regulatory limitations and requirements may be storedin a table in the controlled content repository 102. In addition tostorage and development of content, the controlled content repository102 may also store an audit trail, tracking exact content ofcommunications as they were sent by the user, as well as metadata aboutwebinars regarding the content shared with customers.

The customer relationship management subsystem 104 contains all contactinformation that may be available to users. In addition to storage ofcontact information, the customer relationship management subsystem 104may also be capable of storing configurations regarding specificpreferences, regulatory limitations and requirements, and other fieldsthat will facilitate the generation of appropriate approved electroniccommunications, in general or on a by-recipient basis. These preferencesand/or requirements include both the preferences of the user (e.g.,maintaining account lists) as well as the preferences of the enterprise(e.g., employers of the users), discussed in further detail below. Insome examples, the approved content may be pre-processed and stored inthe controlled content repository 102 and provided to the multichannelprocessing engine 108 and the customer relationship management subsystem104 during a webinar. In other examples, the customer relationshipmanagement subsystem 104 may have a content management subsystem and mayprovide the approved content. The customer relationship managementsubsystem 104 may store event related data, e.g., a link to approvedcontent in the controlled content repository 102, an attendee list, aspeaker list, and webinar tracking information, as will be described indetail below.

In this embodiment, the customer relationship management subsystem 104is capable of communication with multiple sources through the customerrelationship management server 106 or through other channels to maintaina current and accurate collection of information regarding customeraccounts. The interface with the multiple sources can be, for example,through an Applications Programming Interface or API, as the APIinterface will allow compatability with a flexible array of third-partyprovider servers. The information being updated may include, but is notlimited to, licensing information, area of practice, and location of thevarious customer contacts. In this manner, the customer relationshipmanagement subsystem 104 pulls the approved version of what representsan account or physician, which then pulls from multiple networks toensure that the information regarding an account is up-to-date.

With further reference to the customer relationship management subsystem104, this system may be a cloud-based customer database that provides acentral access to store and distribute consistent data across customercompanies as well as their possible third-party partners and agenciesthat are used to keep this data updated. This system can providestandard data formats and provide an easy and automated way forcustomers to have access to coordinated and frequently updated CRM dataand to use that coordinated data for sending approved electroniccommunications, e.g., webinar invitations, in accordance with the systemdescribed herein.

In an embodiment, the multichannel processing engine 108 is responsiblefor combining the customer account information from the customerrelationship management subsystem 104 with content available from thecontrolled content repository 102. Within the customer relationshipmanagement subsystem 104, customer accounts may be assigned a set ofalignment rules which determine specific pieces of content available foruse from the controlled content repository 102. The multichannelprocessing engine 108 may apply these rules and supply the user with alist of approved email templates and pieces of content that may then beused to construct an approved email communication (e.g., a webinarinvitation) and shared during a webinar.

An event management controller 130 may control the process to bedescribed with FIG. 3 below, including getting an event approved,sending webinar invitations, starting a webinar and collecting data toupdate the CRM subsystem 104 during the webinar. The event managementcontroller 130 may store event related information, such as informationabout attendees and speakers, event content, and event details. It maybe coupled to a teleconference controller 131 to communicate eventrelated information, schedule events, generate event invitations andrender webinars.

Executable code comprises computer readable instructions stored on thecomputer readable medium (the code storage medium 120). The executablecode storage 120 is in communication with the various computing machinesin the system 100 such as the customer relationship management server106 and the multichannel processing engine 108. The same or anotherexecutable code storage 120 may be accessed by the previously describedcomponents of the controlled content repository 102 for providingseparate computer readable code for operating upon by processingmachines in that system. In all cases, the code is programmed to performthe functions that are described in the present embodiments and/oradditional functions according to system design needs.

Communication between the multichannel processing engine 108 and thecustomer relationship management subsystem 104 may occur via thecustomer relationship management server 106, which acts as an interfacebetween the two. The customer relationship management server 106 may actsolely as an entry and exit point for the customer relationshipmanagement subsystem 104. The user may access the multichannelprocessing engine 108 through either a Web Client 110 or through themobile apps 112 (such as iOS, Android, Blackberry, or Windows Mobilesystems).

FIG. 2 provides a description of the controlled content repository 102with additional specific applications and interfaces connected thereto.In an embodiment, this controlled content repository 102 is acloud-based or distributed network based system for consolidating anenterprise's data, oftentimes integrating multiple content repositoriesin an enterprise into a single system having coordinated control,measuring, and auditing of data creation, access and distribution.

In an embodiment of the controlled content repository 102 for the lifesciences industry, as illustrated in the figure, this repository 102 caninclude specific data collections for the following areas and/orbusiness process-specific front-end applications 204:

The Research & Development (R&D) front end application 208 provides foran aggregation of materials in support of research and initial clinicaltrial submissions through building organized and controlled contentrepositories within the controlled content repository 102. Elements thatcan be stored, organized, and managed through this front end includesubmission bills of materials, Drug Information Association (DIA)reference models support, and submission-ready renderings. This frontend 208 is designed to provide an interface to the controlled contentrepository 102 whereby researchers, contract research organizations(CROs), and other collaboration partners can access and/or distributecontent through a single controlled document system.

The clinical trials front-end application 210 provides for faster andmore organized access to trial documents and reports, while supportingseamless collaboration between sponsors, CROs, sites, investigators andother trial participants. Specific features both ease study and siteadministration as well as support the DIA trial master file (TMF)reference model. Having this front-end application providing access tothe controlled content repository 102 further provides for efficientpassing off of controlled content repository content between this phaseand other phases of the life sciences development process.

The manufacturing and quality application 212 enables the creation,review, approval and distribution of controlled documents across theorganization and with external partners in the context of materialscontrol and other manufacturing elements. The application 212 providesfunctionality in support of the manufacturing process includingwatermarking, controlled print, signature manifestation and “Read andUnderstood” signature capabilities. The documents and metadataassociated with this process is managed and stored in the controlledcontent repository 102 whereby it can be assured that the relateddocuments are not distributed in contravention of law and companypolicy.

The medical communications application 214 provides for communicationswith medical facilities, including call center access, integration, andinterface functionality. Particular access control features and metadataassociated with this application 214 include expiration and periodicreview elements, multi-channel support, global documents and automaticresponse package generation through the controlled content repository102.

The marketing and sales application 216 provides an end-to-end solutionfor the development, approval, distribution, expiration and withdrawalof promotional materials. Specific features include support for globalpieces, approved Form FDA 2253 (or similar international forms) formgeneration, online document, content to be shared during a webinar, andvideo annotation, and a built-in digital asset library (DAL). Again, thecommunications may be through the controlled content repository 102.

In disclosed embodiments, there are provided a number of back-end systemapplications 220 that provide for the management of the data, forms, andother communications in the controlled content repository. For example,the back-end systems applications 220 may include a regulatorycompliance engine 222 to facilitate regulatory compliance, includingaudit trail systems, electronic signatures systems, and systemtraceability to comply with government regulations, such as 21 CFR Part11, Annex 11 and GxP-related requirements. The regulatory complianceengine 222 may include processors for developing metadata surroundingdocument and project folder accesses so from a regulatory compliancestandpoint it can be assured that only allowed accesses have beenpermitted. The regulatory compliance engine 122 may further includesprevalidation functionality to build controlled content in support ofinstallation qualification (IQ) and/or operational qualification (OQ),resulting in significant savings to customers for their systemvalidation costs.

In further disclosed embodiments, the back-end systems 220 may contain areporting engine 224 that reports on documents, their properties and thecomplete audit trail of changes. These simple-to-navigate reports showend users and management how content moves through its life cycle overtime, enabling the ability to track ‘plan versus actual’ and identifyprocess bottlenecks. The reporting engine may include processors fordeveloping and reporting life cycle and document management reportingbased on stored project data and access metadata relative to documents,forms and other communications stored in the controlled contentrepository 102.

In further disclosed embodiments, the back-end systems 220 can includean administrative portal 226 whereby administrators can controldocuments, properties, users, security, workflow and reporting with asimple, point-and-click web interface. Customers also have the abilityto quickly change and extend the applications or create brand newapplications, including without writing additional software code.

In further disclosed embodiments, the back-end systems 220 may include asearch engine 228 whereby the controlled content repository 102 candeliver simple, relevant and secure searching.

In providing this holistic combination of front-end applications 204 andback-end system applications 220, the various applications can furtherbe coordinated and communicated with by the service gateway 230, whichin turn can provide for communications with various web servers and/orweb services APIs 113. Such web servers and/or web services APIs 113 caninclude access to the content and metadata layers of some or all of thevarious applications 204 and systems 220, enabling seamless integrationamong complementary systems.

In the context of the described embodiments, the particular features andcapabilities integrate with the other elements of the event managementsystem 100 such that particular features are usable within the varioususer screens. For example, and without limitation to any other possiblecombination of features, in the below-described description of a webinarin the life science industry, the above-described search portal can beused to search for approved content within the controlled contentrepository 102 which may be then be shared during a webinar. And thesynergy of combining these particular systems is that the generation ofthe controlled content can be done in a controlled fashion such that theapproved content can be sent to customers with greater confidence in theintegrity of the data being sent.

FIGS. 3A, 3B and 3C illustrate a flowchart of a method for managing alife science event according to one embodiment of the present invention.The process may start at 301.

At 303, a first user may login to the event management system 100. Thefirst user may be an employee of a pharmaceutical company.

At 305, a content approval user interface may be displayed so that thefirst user may submit a request for approval of content for a lifescience event. If the pharmaceutical company wants to have some eventsfor the year, it may decide the key topics to cover, and work withdigital agency to develop the content to share.

A request to get the content approved may be received on the contentapproval user interface at 307.

At 309, the content may be approved by a second user, e.g., thepharmaceutical company's lawyer, and stored in the controlled contentrepository 102.

At 311, a request to search the CRM subsystem 104 for physicians, orother health care professionals (“HCP”), specialized in the event topicmay be received from the first user.

At 313, a list of physicians specialized in the event topic may bereturned from the CRM subsystem 104 and displayed.

At 315, a request for approval of one or more of the physicians in thelist to be speaker(s) of the approved event may be received.

At 317, one or more physicians may be approved as speakers of the eventin response to the user request.

At 319, event types and event topics may be displayed so that the firstuser may choose those that the content applies to. The event types andcontent may automatically come from the CRM subsystem 104. Otherproperties associated with the event may be displayed for the first userto choose those that the content applies to as well, e.g., geographiclocations, products, and countries.

In one implementation, the event management system 100 is built on theCRM system and the content is stored in the controlled contentrepository 102. When the user is in the CRM system and created a newtopic, or a new event type, the new topic and/or new event type may beautomatically pushed to the controlled content repository 102. Thecontent in the controlled content repository 102 may be associated tothe topic or event type based on, e.g., relevancy indicated by metadata.When the user is in the controlled content repository 102, and hashis/her content, he/she may be able to choose which event types, and/ortopics this content is related to. In one implementation, themultichannel processing engine 108 may bring the content in thecontrolled content repository 102 to the CRM subsystem 104 and associatethe content to the event. In one implementation, the controlled contentand event may be automatically associated in the CRM subsystem 104.

In one implementation, rules for associating the content to the rightevent and topic may be built up in the multichannel processing engine108. One example of the rule may be, e.g., when an event is about thistopic, use this content. Thus, when a user creates an event and providesevent type of topic, the CRM server 106 may check the rules and pull theright content.

At 321, a user interface 400 may be displayed for the first user tocreate a webinar for the event. As shown, the user interface 400 mayhave areas for collecting information of the webinar, e.g., event name,event type, start time, end time, topic, speakers, attendees andestimated attendance. In one implementation, a list of speakersspecialized on the topic may be obtained from the CRM subsystem 104 anddisplayed for the user to choose one or more for his event.

At 323, user input may be received on the user interface 400. In oneimplementation, the first user may search the CRM subsystem 104 tochoose attendees of the event.

At 324, controlled content associated with the topic may be displayedfor the user so that he/she can choose the content for his/her event.

At 325, when the user clicks save, a record may be created in the CRMsubsystem 104 for the event which may include information about itsname, type, start time, end time, topic, speakers, attendees, type, andrelated controlled content.

At 331, an invitation may be generated for each speaker and attendee andsent out. The speaker and attendee contact information may be obtainedfrom the CRM subsystem 104, and the invitation may be an email generatedby the multichannel processing engine 108.

In one implementation, a unique identifier may be generated for eachrecipient and included in his/her invitation. In one implementation, theunique identifier may be a unique URL for each recipient.

In one implementation, the invitation may be sent via an approved emailgenerated by the approved email generation controller 109, as describedin U.S. Pat. No. 9,055,023, entitled System and Method for ControllingElectronic Communications and issued on Jun. 9, 2015, which is herebyincorporated by reference herein for all purposes.

Recipients may receive their invitations, including the unique links, intheir inboxes. When a speaker clicks on his/her link at 341, it may bedetermined if the event management client is installed on his/her deviceat 342.

If not, it may be installed at 343.

When the event management application is installed on a speaker'sdevice, at 345, an information screen for the event may be displayed,which may provide the speakers information such as time and name of theevent, and its description, as shown in FIG. 5. The information screenmay also include any presentation that is approved for this event. Thespeaker may click on that presentation, download it, and then practicethe content.

In one implementation, when a new version of the content is uploaded, orthe current version is updated, an indicator may be displayed toindicate that a new version is available, so that the user can beprompted to download the new version of the content. The content may becoming from the controlled content repository 102. The contentmanagement server 101 may check when the user loads the event and theversion of the content he/she has. If the version on his/her device isnot the same as the latest version, the speaker may be informed to getan update. So before the event, the speaker can practice, and downloadnew version of the content that is needed. In one implementation, when achange is made to the content in the controlled content repository 102,the multichannel processing engine 108 may pick up the change, and pushit to the CRM subsystem 104 and the event management client on thespeaker's computing device. Consequently, the speaker can get the latestversion of the controlled content, and only the latest version of thecontrolled content will be shared.

On the day of the event, the first user may start a webinar of the eventat 351. At 353, the speaker may join the webinar of the event.

At 355, the attendees may join the webinar of the event.

At 357, the speaker may start to share the approved content of theevent. In one implementation, when a participant clicks on “sharescreen”, the event management controller 130 will only allow the speakerto share the latest approved version of content. If the speaker has anold version of the content, the event management controller 130 may givehim/her a chance to update to the newest version.

In one implementation, when the speaker selects the presentation andstarts to share a slide, the slide sorter may be displayed on the sideon the screen shared to make it easy for the speaker to move betweenslides.

At 358, the event management controller 130 may track the content shown,including which slide is showing, for how long, and the order of theslides. The data may be stored in the controlled content repository 102or the CRM subsystem 104 for auditing purposes. For example, the lifescience industry is very strict about having the right contentdisplayed, including having the latest version of approved contentdisplayed, and making sure that the correct slide was shown for theproper amount of time. With slide tracking, the system 100 mayautomatically store data that says, e.g., the speaker spent 3 minutes onthe side effect slide and 2 minutes on the dosing slide.

At 359, the event management controller 130 may track the attendees'participation data, e.g., their join and leave times, and store the datain the controlled content repository 102 or the CRM subsystem 104.

The first user may end the webinar at 361.

At 363, the participants' account information in the CRM subsystem 104may be updated. In addition to information of the webinar, e.g., itstopic, time and location, the updates for an attendee may include whenhe/she joined, when he/she left and content he/she watched, the updatesfor a speaker may indicate that he/she spoke at the webinar, and thecontent he/she shared.

While a sales representative and an HCP are in a remote meeting via theInternet, the HCP may have some medical inquiries about a pharmaceuticalproduct. The medical inquiry could be off label questions about thepharmaceutical product, for example, if Coldcap can be used to treatheadache. The medical inquiry may be received by the salesrepresentative in various formats, e.g., conversation between the salesrepresentative and the HCP during the virtual meeting. In order to get aresponse to the medical inquiry from the pharmaceutical company, the HCPmust sign a medical inquiry form, so that the actual medical inquiry canbe captured by the sales representative in the CRM.

FIG. 6 illustrates an example flowchart of a method for processing aremote medical inquiry during a remote meeting according to oneembodiment of the present invention. The process may start at 601.

At 603, a sales representative and an HCP may start a remote meeting viathe system shown in FIG. 1.

At 605, a medical inquiry may be received by the sales representativefrom the HCP during their conversation via the remote meeting controlledby the mobile application 112 on the sales representative computingdevice, which communicates with the system 100 including the CRM server106. The medical inquiry could be, for example, if Coldcap can be usedto treat headache.

At 607, a medical inquiry form template user interface may be generatedand displayed by the mobile application 112 on the sales representativecomputing device, which communicates with the system 100 including theCRM server 106, in response to a user request, e.g., a request from thesales representative. The medical inquiry form template may have anumber of areas for receiving the medical inquiry information, e.g., thename of the product, the medical inquiry, the method for receiving theresponse, and the name of the HCP.

At 609, medical inquiry information may be received on the medicalinquiry form template user interface via the mobile application 112 onthe sales representative computing device, which communicates with thesystem 100 including the CRM server 106, from the sales representative.The medical inquiry information may be, for example:

Product requested: Coldcap;

Medical inquiry: if Coldcap can be used to tread headache;

Delivery method: email at Jane.smith@abcclinic.com;

Name of the HCP: Dr. Jane Smith

At 611, a medical inquiry form may be generated by the mobileapplication 112 on the sales representative computing device, whichcommunicates with the system 100 including the CRM server 106, based onreceived medical inquiry information. In addition to the medical inquiryinformation, the medical inquiry form may also include a disclaimer anda signature box.

At 613, the medical inquiry form may be sent by the mobile application112 on the sales representative computing device, which communicateswith the system 100 including the CRM server 106, to the HCP's computingdevice via a second communication channel. The second communicationchannel is separate from the communication channel for the remotemeeting between the sales representative and the HCP, and may be aplatform for building real-time streaming data pipelines andapplications, e.g., MSK Kafka. The second communication channel couldalso use other platforms, e.g., Web Sockets.

At 615, the medical inquiry form may be received and displayed by theHCP computing device.

The HCP may review the medical inquiry form and the disclaimer of themedical inquiry form displayed on her computing device. At 617, asignature may be received at the signature box on the medical inquiryform.

At 619, the signed medical inquiry form may be sent from the HCP deviceback to the sales representative computing device via the secondcommunication channel. The sales representative may review thatsignature and accept the signature.

At 621, the signed medical inquiry from may be saved to the CRMsubsystem 104 via the mobile application 112 on the sales representativecomputing device.

At 623, a call report for the remote meeting may be generated and savedin the CRM subsystem 104 and a flag may be marked to indicate that thesignature was captured through a remote process.

The medical inquiry may be forwarded to the manufacturer and theresponse from the manufacturer may be sent to the HCP based oninformation on the signed medical inquiry form.

The process in FIG. 6 may be used in remote meetings with multiple HCPs,and some HCPs may be face to face, while others are remote.

The flowcharts do not mean to limit the sequence of the steps.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above described exemplary embodiments, butshould be defined only in accordance with the claims and theirequivalents for any patent that issues claiming priority from thepresent provisional patent application.

For example, the multichannel processing engine 108 is shown tocommunicate with only one customer relationship management subsystem 104in the drawings, but it may communicate with more customer relationshipmanagement subsystems. For example, as referred to herein, a machine orengine may be a virtual machine, computer, node, instance, host, ormachine in a networked computing environment. Also as referred toherein, a networked computing environment is a collection of machinesconnected by communication channels that facilitate communicationsbetween machines and allow for machines to share resources. Network mayalso refer to a communication medium between processes on the samemachine. Also as referred to herein, a server is a machine deployed toexecute a program operating as a socket listener and may includesoftware instances.

In all descriptions of “servers” or other computing devices herein,whether or not the illustrations of those servers or other computingdevices similarly show a server-like illustration in the figures, itshould be understood that any such described servers or computingdevices will similarly perform their described functions in accordancewith computer-readable instructions stored on a computer-readable mediathat are connected thereto.

Resources may encompass any types of resources for running instancesincluding hardware (such as servers, clients, mainframe computers,networks, network storage, data sources, memory, central processing unittime, scientific instruments, and other computing devices), as well assoftware, software licenses, available network services, and othernon-hardware resources, or a combination thereof.

A networked computing environment may include, but is not limited to,computing grid systems, distributed computing environments, cloudcomputing environment, etc. Such networked computing environmentsinclude hardware and software infrastructures configured to form avirtual organization comprised of multiple resources which may be ingeographically disperse locations.

The approved content may be in any format, e.g., text, audio, video,picture, multimedia, or PDF.

Various terms used herein have special meanings within the presenttechnical field. Whether a particular term should be construed as such a“term of art,” depends on the context in which that term is used.“Connected to,” “in communication with,” or other similar terms shouldgenerally be construed broadly to include situations both wherecommunications and connections are direct between referenced elements orthrough one or more intermediaries between the referenced elements,including through the Internet or some other communicating network.“Network,” “system,” “environment,” and other similar terms generallyrefer to networked computing systems that embody one or more aspects ofthe present disclosure. These and other terms are to be construed inlight of the context in which they are used in the present disclosureand as those terms would be understood by one of ordinary skill in theart would understand those terms in the disclosed context. The abovedefinitions are not exclusive of other meanings that might be impartedto those terms based on the disclosed context.

Words of comparison, measurement, and timing such as “at the time,”“equivalent,” “during,” “complete,” and the like should be understood tomean “substantially at the time,” “substantially equivalent,”“substantially during,” “substantially complete,” etc., where“substantially” means that such comparisons, measurements, and timingsare practicable to accomplish the implicitly or expressly stated desiredresult.

Additionally, the section headings herein are provided for consistencywith the suggestions under 37 CFR 1.77 or otherwise to provideorganizational cues. These headings shall not limit or characterize theinvention(s) set out in any claims that may issue from this disclosure.Specifically and by way of example, although the headings refer to a“Technical Field,” such claims should not be limited by the languagechosen under this heading to describe the so-called technical field.Further, a description of a technology in the “Background” is not to beconstrued as an admission that technology is prior art to anyinvention(s) in this disclosure. Neither is the “Brief Summary” to beconsidered as a characterization of the invention(s) set forth in issuedclaims. Furthermore, any reference in this disclosure to “invention” inthe singular should not be used to argue that there is only a singlepoint of novelty in this disclosure. Multiple inventions may be setforth according to the limitations of the multiple claims issuing fromthis disclosure, and such claims accordingly define the invention(s),and their equivalents, that are protected thereby. In all instances, thescope of such claims shall be considered on their own merits in light ofthis disclosure, but should not be constrained by the headings set forthherein.

What is claimed is:
 1. A machine-implemented method for processing amedical inquiry, the method comprising: establishing a controlledcontent repository, the controlled content repository being securely andcontrollably accessed; establishing an access protocol for thecontrolled content repository; receiving an input for approving an itemof content to be stored in the controlled content repository; storingapproved content within the controlled content repository, whereby theapproved content is stored in the controlled content repositoryaccording to the access protocol and whereby the access protocolcomprises at least one set of alignment rules for determining if a firstitem of approved content within the controlled content repository can bemade available to a first customer; receiving the medical inquiry at afirst user computing device from a second user computing device via afirst communication channel, wherein the medical inquiry is related to amedical product, and wherein the first communication channel is carriedout according to a first communication protocol; generating a medicalinquiry form comprising information related to the medical inquiry; andtransmitting the medical inquiry form from the first user computingdevice to the second user computing device via a second communicationchannel, wherein the second communication channel is carried outaccording to a second communication protocol.
 2. The method of claim 1,wherein the first communication channel is over the Internet.
 3. Themethod of claim 1, wherein the second communication channel is aplatform for building real-time data streaming.
 4. The method of claim1, wherein the second communication protocol is MSK Kafka.
 5. The methodof claim 1, wherein the second communication protocol is Web Sockets. 6.The method of claim 1, further comprising: generating a medical inquiryform template on the first user computing device in response to themedical inquiry, wherein the medical inquiry form template comprises afirst area for receiving a first piece of information in the medicalinquiry, and a second area for receiving a second piece of informationin the medical inquiry.
 7. The method of claim 6, wherein the firstpiece of information in the medical inquiry is a name of the medicalproduct.
 8. The method of claim 6, further comprising: receiving thefirst piece of information in the medical inquiry in the first area, andreceiving the second piece of information in the medical inquiry in thesecond area.
 9. The method of claim 1, wherein the medical inquiry formcomprises a disclaimer.
 10. The method of claim 1, wherein the medicalinquiry form comprises a signature box.
 11. The method of claim 1,further comprising: receiving a signed medical inquiry form at the firstuser computing device from the second user computing device via thesecond communication channel.
 12. The method of claim 11, furthercomprising: storing the signed medical inquiry from to a customerrelationship management (“CRM”) system.
 13. The method of claim 1,wherein the medical inquiry is received during a remote meetingconducted via the first communication channel.
 14. The method of claim13, further comprising: obtaining attendee information of the remotemeeting from a customer relationship management (“CRM”) system.
 15. Themethod of claim 14, further comprising: storing a report of the remotemeeting to the customer relationship management (“CRM”) system.
 16. Themethod of claim 1, further comprising: sending a response to the medicalinquiry to the second user computing device.